docs(feat[api-style]): Visual improvements to API docs via gp-sphinx#53
Merged
docs(feat[api-style]): Visual improvements to API docs via gp-sphinx#53
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #53 +/- ##
=======================================
Coverage 96.89% 96.89%
=======================================
Files 5 5
Lines 129 129
=======================================
Hits 125 125
Misses 4 4 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…i-style why: Add type and modifier badges to autodoc entries. what: - Add sphinx_autodoc_api_style to extra_extensions in docs/conf.py
…to 0.0.1a5 why: Align docs dependencies with latest gp-sphinx workspace releases. what: - Pin sphinx-autodoc-api-style and bump gp-sphinx packages to 0.0.1a5 - Regenerate uv.lock
why: Align dev docs dependencies with gp-sphinx 0.0.1a6 on PyPI. what: - Bump gp-sphinx ecosystem pins in pyproject.toml - Regenerate uv.lock
why: Pick up the sphinx-argparse-neo multi-page duplicate-label scoping fix landed in gp-sphinx PR #16 so docs builds on this branch emit fewer duplicate label warnings. what: - Bump gp-sphinx and sibling package pins from 0.0.1a6 to 0.0.1a7 - Regenerate uv.lock
why: Capture the api-styling migration to the gp-sphinx package stack in the unreleased notes. what: - Add a Documentation bullet under g 0.0.10 linking to the project PR
tony
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adopt the gp-sphinx Sphinx package stack for g's API documentation. The net visual effect is card-style autodoc signatures with safety and scope badges, MyST cross-reference roles for Python objects, scoped section names in multi-page CLI docs, and polished IBM Plex typography — all landing together from the
gp-sphinx 0.0.1a7pre-release.What's new
sphinx-autodoc-api-style— card layouts, badges, MyST roles for Python objectssphinx-autodoc-badges— consistent XS/SM/LG/XL size variants with WCAG-AA contrastsphinx-argparse-neo— CLI doc builds no longer emitduplicate labelwarnings (gp-sphinx#16)sphinx-fonts— IBM Plex Sans and Mono at full weight range, zero-CLS loadingVerification
uv run ruff check . --fix --show-fixesuv run ruff format .uv run mypyuv run py.test --reruns 0 -vvvjust build-docsAll pass on the branch tip. See gp-sphinx 0.0.1 release notes for the full list of changes covering
0.0.1a1..0.0.1a7.